How to determine ownership of a project

Hi,

Is it possible to link a user to a project? Since projects don't possess an 'owner' property, I was hoping there would be some viable alternative. Obviously I'm not familiar enough with DOORS to know of these other options, but I am exploring ...

Regardless, can anyone help?

Thanks
meherts - Tue Jun 01 16:07:31 EDT 2010

Re: How to determine ownership of a project
Mathias Mamsch - Tue Jun 01 16:32:23 EDT 2010

Usually people will put the owner into the project description. Since a project has no attributes, you need to find some solution for you, depending on what you want to do with it!

Some more ideas:
You could put an "Owner" module in the project.
You could associate the users with the project using the user properties.
You could create a custom module, where you store the owners of each project.
You can define an empty baselineset or partition on the project with the owner name (arg!)
You can give this one user explicit RMCDA rights on the project.

Regards, Mathias
Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

Re: How to determine ownership of a project
llandale - Tue Jun 01 17:21:14 EDT 2010

Mathias Mamsch - Tue Jun 01 16:32:23 EDT 2010
Usually people will put the owner into the project description. Since a project has no attributes, you need to find some solution for you, depending on what you want to do with it!

Some more ideas:
You could put an "Owner" module in the project.
You could associate the users with the project using the user properties.
You could create a custom module, where you store the owners of each project.
You can define an empty baselineset or partition on the project with the owner name (arg!)
You can give this one user explicit RMCDA rights on the project.

Regards, Mathias

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

... or create a user 'group' called "<ProjName>_Owners", insert the owners, and of course provide them RMCDA access.

I wrote a rather sloppy script to count Create and Modify History of all modules in a folder and below, to figure out how old the data is but also to figure out who did the most work in it. Quite clumsy and useless.

  • Louie

Re: How to determine ownership of a project
meherts - Wed Jun 02 08:49:56 EDT 2010

Mathias Mamsch - Tue Jun 01 16:32:23 EDT 2010
Usually people will put the owner into the project description. Since a project has no attributes, you need to find some solution for you, depending on what you want to do with it!

Some more ideas:
You could put an "Owner" module in the project.
You could associate the users with the project using the user properties.
You could create a custom module, where you store the owners of each project.
You can define an empty baselineset or partition on the project with the owner name (arg!)
You can give this one user explicit RMCDA rights on the project.

Regards, Mathias

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

I appreciate the enumeration (really, I do), but I find myself confused by the second item on your list: "You could associate the users with the project using the user properties".

One user property I attempted to use was 'class', but I did not see any explicit way of associating a user with a specific project. Perhaps you can elaborate?

Anyway, I appreciate te suggestions - if neither of you mind, I may try implementing them.

Re: How to determine ownership of a project
meherts - Wed Jun 02 08:56:21 EDT 2010

meherts - Wed Jun 02 08:49:56 EDT 2010
I appreciate the enumeration (really, I do), but I find myself confused by the second item on your list: "You could associate the users with the project using the user properties".

One user property I attempted to use was 'class', but I did not see any explicit way of associating a user with a specific project. Perhaps you can elaborate?

Anyway, I appreciate te suggestions - if neither of you mind, I may try implementing them.

Hmm ... just shooting in the dark, but were talking about the set(user property) function? If so, I could use this function to create a custom property, say 'Owner', and set the value of this property to a specific project.

Re: How to determine ownership of a project
llandale - Wed Jun 02 10:53:18 EDT 2010

meherts - Wed Jun 02 08:56:21 EDT 2010
Hmm ... just shooting in the dark, but were talking about the set(user property) function? If so, I could use this function to create a custom property, say 'Owner', and set the value of this property to a specific project.

... or have one for each Project name you care about, with basically a true or null value for each user. using 'Owner' would require you to list all the Projects the user owns, which I guess is not so bad.

Re: How to determine ownership of a project
Mathias Mamsch - Wed Jun 02 11:07:03 EDT 2010

meherts - Wed Jun 02 08:56:21 EDT 2010
Hmm ... just shooting in the dark, but were talking about the set(user property) function? If so, I could use this function to create a custom property, say 'Owner', and set the value of this property to a specific project.

I stumbled upon this a while ago - the User datatype really has custom properties which are not accessible by the DOORS client (like the configuration area), just by DXL. In the DXL help they are documented.

I don't know what kind of access rights you need to have to modify them, but I guess you must be able to manage users. Since this is typically an admin right you might not be able to use them.

Regards, Mathias
  

// Updates the value of the specified string property within user. 
// If the property does not exist it is created. 
void set(User user, string property, string value) 
 
// Deletes the specified user defined string property within user. 
void delete(User user, string property) 
 
// Returns the value of the specified user defined string property 
// within user. 
string get(User user, string property)

 

 

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

 

 

Re: How to determine ownership of a project
meherts - Wed Jun 02 11:11:43 EDT 2010

Mathias Mamsch - Wed Jun 02 11:07:03 EDT 2010

I stumbled upon this a while ago - the User datatype really has custom properties which are not accessible by the DOORS client (like the configuration area), just by DXL. In the DXL help they are documented.

I don't know what kind of access rights you need to have to modify them, but I guess you must be able to manage users. Since this is typically an admin right you might not be able to use them.

Regards, Mathias
  

// Updates the value of the specified string property within user. 
// If the property does not exist it is created. 
void set(User user, string property, string value) 
 
// Deletes the specified user defined string property within user. 
void delete(User user, string property) 
 
// Returns the value of the specified user defined string property 
// within user. 
string get(User user, string property)

 

 

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

 

 

I have full database credentials ... and those are the methods I used.

Thanks